Preview of Compressed File Email Attachments

ABSTRACT

A system and method of generating a preview of a file attachment includes receiving the file attachment in an email server. The file attachment can be received either during composition of the email or when receiving an inbound email. Determining if the file attachment is a previewable file type or compressed file type or non-previewable file type and automatically generating a preview of the file attachment including identifying the file attachment, parsing the file attachment to identify content of the file attachment, wherein the identified content includes a pagination of the file attachment. A file structure for each page of the file attachment is created and then saved to an attachment store in the email server.

BACKGROUND

Emails are often sent with compressed and uncompressed files attached. The compressed file attachment can include multiple individual files and a file structure that organizes the individual files. When a user receives an email with a compressed file attached, the email application cannot provide a preview to each of the individual files included in the compressed file attachment. Further, the email application cannot provide access each one of the individual files in the compressed file attachment. When a user receives an email with an uncompressed file attached, the email application typically does not generate a preview of the uncompressed file until the user opens the email.

A typical email application requires the compressed file attachment to be downloaded before the contents of the compressed file attachment can be accessed or any of the individual files inside the compressed file attachment can be accessed or even previewed. The downloaded compressed file must then be decompressed and saved in the decompressed format before each of the individual files and file structure of the individual decompressed files can be accessed. Each of the individual decompressed files must be individually selected and accessed to be reviewed. The file structure provides the organization of the individual decompressed files included in the compressed file attachment. The file structure can only be accessed or even previewed after the compressed file attachment has been decompressed and the individual decompressed files and file structure have been saved.

The typical email application user experience is cumbersome and prevents seamless use and sharing of compressed file attachments.

SUMMARY

Broadly speaking, the present invention fills these needs by providing a system and method for automatically generating previews of a compressed file attached to a received email. The compressed file can include multiple, individual files and a file structure organizing the individual files. The preview provides access to each of the individual files and can also allow access to view and navigate the file structure, all without requiring the user to download the compressed file attachment. It should be appreciated that the present invention can be implemented in numerous ways, including as a process, an apparatus, a system, computer readable media, or a device. Several inventive embodiments of the present invention are described below.

One embodiment provides a method of generating a preview of a file attachment includes receiving the file attachment in an email server. The file attachment can be received either during composition of the email or when receiving an inbound email. Determining if the file attachment is a previewable file type or compressed file type or non-previewable file type and automatically generating a preview of the file attachment including identifying the file attachment, parsing the file attachment to identify content of the file attachment, wherein the identified content includes a pagination of the file attachment. A file structure for each page of the file attachment is created and then saved to an attachment store coupled to the email server.

Another embodiment provides a system for receiving an email with a compressed file attachment, identifying the type of the compressed file attachment, identifying a file decompression module corresponding to the type of compressed file attachment, activating the decompression module to decompress the compressed file attachment to produce a decompressed file and to output the decompressed file for preview and storage. Decompressing the compressed file attachment can also include decompressing a file structure included in the compressed file attachment. The file structure can also be stored. The file structure can then be used to navigate to an individual decompressed file included in the compressed file attachment. Once navigated to, the individual decompressed file can be previewed and/or stored.

Decompressing the file attachment to generate previews of the individual files and the file structure included in the compressed file attachment can be accomplished automatically without receiving a user initiation of the decompression process. Thus, when the user selects a preview of individual files, the files are already available for preview.

Yet another embodiment provides a method of generating previews of a compressed file attachment to a received email. The method includes receiving an email with a compressed file attachment, identifying the compressed file attachment type, identifying a file decompression module corresponding to the type of compressed file attachment, activating the decompression module to decompress the compressed file attachment to produce a decompressed file and to output the decompressed file for preview and storage.

Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings.

FIG. 1A is a network diagram of an online email service, in accordance with embodiments of the present disclosure.

FIG. 1B is a flowchart diagram that illustrates the method operations performed in preparing a preview of a file that can be attached to an email, for implementing embodiments of the present disclosure.

FIG. 1C is a flowchart diagram that illustrates the method operations performed in preparing a preview of a file attachment to an email, for implementing embodiments of the present disclosure.

FIG. 2 is a screen capture of a displayed email, in accordance with embodiments of the present disclosure.

FIGS. 3-5 are screen captures of the displayed email after having selected the individual file DSC1100.jpg, in accordance with embodiments of the present disclosure.

FIGS. 6 and 7 are screen captures of a displayed email after having selected the individual file feedbackform.pdf, in accordance with embodiments of the present disclosure.

FIG. 8A is a screen capture of a displayed email after having selected the selectedshot.jpg, in accordance with embodiments of the present disclosure.

FIG. 8B is a screen capture of a displayed email with a full screen view of the selectedshot.jpg, in accordance with embodiments of the present disclosure.

FIG. 9 is a logic processing flow diagram of the email server, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

Several exemplary embodiments for a system and method for automatically generating previews of compressed file attachments and uncompressed file attachments to that may be attached to an email will now be described. It will be apparent to those skilled in the art that the present invention may be practiced without some or all of the specific details set forth herein.

The compressed file attachment can include multiple individual files and a file structure that organizes the individual files. Having direct access to the individual files and to be able to see the file structure that organizes the individual files in the compressed file attachment improves the user experience of receiving the compressed file attachment in the email by reducing the steps required to access the individual files and making the compressed status of the compressed file attachment substantially invisible to the user viewing the received email.

The uncompressed file can be any one of several types of files that can be previewed. A nonexhaustive list of examples of types of files include document files, spreadsheet files, text files, presentation files, many types of image files, formatted files such as PDFs, slideshows and many other types of files.

FIG. 1A is a network diagram of an online email service 100, in accordance with embodiments of the present disclosure. The online email service 100 includes a host service 120. The host service 120 provides a user interface 122 for a user to interact with the email service. The user interface 122 displays emails to the user and provides an access for the user to read, write, save, edit, send, receive and otherwise interact with the emails.

The host service 120 can be a client device such as a personal computer or a handheld computing device such as a smart phone or a tablet. The host service 120 can also be a web hosted service provided on a server accessible via the Internet 102 or some other network using a browser application or a specific email application. The host service 120 is coupled to the Internet 102 with a network 104. The host service 120 is also coupled to an email server 110 by the network 104 and/or the Internet 102 and a network 106. The networks 104 and 106 can be local networks, wired or wireless networks and combinations thereof.

The email server 110 is also coupled to a store 112 for storing emails and other data related to emails such as compressed and uncompressed files that are attached to or can be attached to emails. The email server 110 includes application modules for receiving, storing, processing, displaying, writing and sending and any other functional processing of emails.

FIG. 1B is a flowchart diagram that illustrates the method operations 150 performed in preparing a preview of a file that can be attached to an email, for implementing embodiments of the present disclosure. The operations illustrated herein are by way of example, as it should be understood that some operations may have sub-operations and in other instances, certain operations described herein may not be included in the illustrated operations. With this in mind, the method and operations 150 will now be described.

In an operation 151, a file attachment received in the email server. The file attachment may be received when an email with the file attachment is received an email server. The file attachment may also be received by the email server, as a user is composing an email and selects a file to attach to the email the user is composing.

In an operation 152, the email server reviews the file type of the file attachment to determine if the file type is one that the email server is configured for producing a preview able version of the file attachment. There many types of file attachments that could be received. Some examples might include an MS Word document file, and ASCII text file, a presentation files such as MS PowerPoint or similar presentations, a spreadsheet file, a formatted document file like an Adobe PDF formatted document, many types of image files such as a jpeg, gif, tif and any other standard image files, a slides show file, a video file in any of the various video formats, an audio file in any of the various audio formats, and many other well-known types of files that the email server may be configured for identifying. If the file attachment is pre-viewable then the method operations continue in an operation 158, as described below. If the file attachment is not pre-viewable in the method operations continue in operation 154 as follows.

In operation 154, the file attachment is examined to determine if it is a compressed file type. Compressed file attachment can include a zipped file or many other types of file compression formats. If the file attachment is not a compressed file and not a pre-viewable file as described in operation 152 above and the method operations continue in an operation 155.

In operation 155, a non-previewable file notification is generated and saved on the server. The non-previewable file notification can include a thumbnail that may be a representation of the type of file. As an example, if the file attachment is an executable file, then a small image of “EXE” or similar thumbnail may be generated. If the email server is unable to identify the file type of the file attachment, then a generic “non-previewable file” thumbnail may be associated with the file attachment on the email server.

Referring again to operation 154 above, if the file attachment is a compressed file type there may be multiple individual files within the compressed file attachment. Generally, a small number of individual files within the compressed file attachment would be easily dealt with as will be described below. However, often compressed file attachments can include many even hundreds or thousands of individual files. Thus, in an operation 156, the compressed file attachment is examined to determine if the compressed file attachment includes two numerous of the individual files to effectively generate a useful preview of all of the individual files. The limit for the number of individual files in the compressed file attachment can be set by the user or an email server setting or many other ways. In a typical example the number of individual files in the compressed file attachment would probably be limited to about ten as more than ten previews would tend to clutter the email when viewed by a user and thus make the previews less user-friendly and less useful by the user. Again is important understand that this limit is a selectable limit and the example limit of ten individual files in the compressed file attachment is merely an example and not a specific embodiment or limitation in any number of individual files could be selected as the limit.

If an operation 156, the number of individual files in the compressed file attachment is greater than the limit, then the method operations continue in operation 155 as described above and no preview of the individual files is generated and instead an appropriate non-previewable notification is generated and associated with the compressed file attachment.

If in operation 156, the number of individual files in the compressed file attachment is less than the limit, then the method operations continue in an operation 157. In operation 157, the email server activates a corresponding decompression application to perform a decompression operation of the compressed file attachment and extract each of the individual files from the compressed file attachment. The email server can activate the corresponding decompression application though calling the decompression application through a corresponding application program interface. The number of different types of decompression applications the email server may access is limited only by those decompression applications that are available to the email server.

In an operation 158, the individual extracted files from the compressed file attachment in operation 157 or the single, previewable, file attachment from operation 152, is stored in a file attachment store such as my be included in the store 112. And the method operations continue in operation 160 where the preview of each of the file attachments is generated. Operation 160 is described in more detail in FIG. 1C as described below.

In an operation 170, the email server receives a request for preview of a selected page of a file attachment. This request for preview the selected page of the file attachment would typically occur when the user opens an email including the file attachment. It should be noted that the preview of the file attachment is generated before the email is opened by a user and is generated automatically when the email server receives the file attachment and without requiring receiving a request to generate the preview.

In an operation 172, the email server responds to the request for preview of the selected page of a file attachment by sending a preview of the selected pages to the user's user interface to the email server. One approach to sending a preview of the selected pages includes fetching a parent frame from the file attachment store coupled to the email server. The parent frame pulls the page data that was extracted from the selected page, or pages, of the file attachment. The parent frame and a properly formatted cascading style sheets provide formatting for the page data that was extracted from the selected page of the file attachment. The parent frame provides for a simple and efficient assembly of an HTML representation of the selected page within the email user interface as will be described in more detail below. Another approach to sending a preview of the selected pages could include opening a browser tab for presenting the preview instead of presenting the preview within the email user interface. Another approach can include using an image overlay such as scalable vector graphics with a text overlay as a preview of the selected page of the file attachment.

The parent frame can be stored with the page data that was extracted from the selected page. HTML frames, such as the parent frame, allow a page author to present the information in the HTML page in multiple views. Views may be independent windows or subwindows. Multiple views offer the page author different ways to present selected information, while other information in views can be viewed or presented by scrolling. In one example, using three frames: a first frame for a static banner, a second frame for a navigation menu, and third frame for a main view that can be scrolled though or replaced by clicking on an item in the third frame. Multiple different parent frames can be defined and saved by the server at some time before the file attachment is received by the server. By way of example, certain parent frames may be optimized and associated for use with text or document file attachments while a different parent frame may be optimized and associated for use with a file attachment including one or more images and yet a third parent frame that may be optimized and associated for use with file attachment that includes one or more images and text. When the server identifies the file type and or content of the file attachment, a corresponding parent frame can be selected that is optimized for that type of file attachment or the content included in the file attachment.

FIG. 1C is a flowchart diagram that illustrates the method operations 160 performed in preparing a preview of a file attachment to an email, for implementing embodiments of the present disclosure. The operations illustrated herein are by way of example, as it should be understood that some operations may have sub-operations and in other instances, certain operations described herein may not be included in the illustrated operations. With this in mind, the method and operations 160 will now be described.

In an operation 161, one of the file attachments saved in the file attachment store is selected for generating a preview of the file attachment. The order of selecting the files from the file attachment store can be defined any suitable manner. By way of example, a user preference could be selected or captured so that file types that are most likely to be desired for preview may be selected before file types that are less likely to be desired for preview. Which file types are most likely to be desired or less likely to be desired for preview can be captured according to prior user use patterns. For example if the user prefers seeing documents as previews than a document file would have a preview generated before other types of documents. For another user that prefers previews of image files, then file attachments of images could be used to generate previews first.

In an operation 162, the selected file is identified. One approach to identifying the file is to perform a hash operation on the selected file to generate a unique file identifier. The file identifier can then be used to uniquely identify the file.

In an optional operation 163, file identifier is used to determine if the selected file is a duplicate file. This optional operation 163 streamlines the email servers processes by preventing unnecessary duplication if a preview of the file attachment has been previously generated. If the selected file is a duplicate file, then the method operations continue in an operation 164 and the selected file is linked to an existing file preview in the file attachment store.

If the selected file is not a duplicate file in the method operations continue in an operation 165. In operation 165, the selected file is parsed to identify the content of the selected file. For example, if the selected file included multiple pages, formatted text and multiple images, then the file would be examined to first identify each and every page of the selected file. Next each page would be parsed to identify the contents of each page.

In an operation 166, a file structure is created for each page of the selected file and the corresponding data is saved in each of the file structures for each page in an operation 167. The file structure for each page includes the unique document identifier, the page identifier and HTML contents folder including all of the data required to create an HTML representation of that page of the selected file. In one implementation, the HTML contents folder would include the cascading style sheets and the various HTML files. Dividing the selected file into multiple individual pages allows previews of selected pages to be served to the user more efficiently and simply than requiring serving a preview of all of the pages of the selected file. Dividing the selected file in the multiple individual pages may also require accessing a corresponding application to open the selected file by a corresponding application program interface. It should be understood that, the different types of files that can be previewed is limited only by the email server having access to the corresponding applications needed to access the selected file.

The file structure for each page can also include a thumbnail such as a small graphical representation of the page. In one example the thumbnail is limited to a very finite size such as 36×36 pixels. This is merely an example as a thumbnail could be any suitable size that might be chosen.

After the file structure for each page is saved the method operations of 160 are repeated for each additional document and then the method operations can continue in operation 170 as discussed above in FIG. 1B.

As the preview of each of the file attachments includes individual previews of each page of the file attachment, then the pages of the file attachment can be previewed sequentially if the user desires, but can also be previewed randomly. For example if a document file attachment includes 15 pages, and the user is interested in the content of page 12, the user can directly select a preview of page 12, rather than selecting the entire 15 page document and scanning or paging through to access page 12.

FIG. 2 is a screen capture of a displayed email 200, in accordance with embodiments of the present disclosure. The displayed email 200 includes a header portion 201 that includes functionality for the user to access their emails. The header portion 201 can include an identifier for the owner of the email inbox “Jennifer” in the upper right corner. The header portion 201 can also include other functionality such as accessing other services such as News, Sports, Weather, etc. provided by the email service provider.

The various buttons and identifiers can also include optional icon representations such as the icon adjacent to the “Jennifer” identifier on the email inbox. The icons can include functionality such as accessing additional information about that button (e.g., can provide access to Jennifer's profile page) or can merely be an additional graphic to add to the page such as a thumbnail of Jennifer's face. Similar icons and thumbnails are provided throughout the displayed email 200.

One portion of the header 210 includes functional buttons such as the icons to the left portion and DELETE, MOVE, SPAM and MORE buttons to choose functions the user is wishes to apply to a selected email. The MORE button provides a menu of less commonly used email processing functions that a user might apply to a selected email.

A list of folders 203 is displayed along the left column of the displayed email 200. The list of folders 203 includes folders that the user may have created to organize previously sent and received emails. The list of folders 203 allows the user to navigate to the folders and access emails stored therein. Also shown in the left column is an optional space 205 for providing ads.

Toward the center of the displayed email 200, is a subject line 208. In this instance the subject line 208 reads “Last night meetup.” Also included in the subject line 208 is a paperclip or similar icon 208A indicating there is one or more files attached to the displayed email 200.

Immediately below the subject line is the email body 202 of the displayed email 200. The email body 202 includes the text of the actual email message sent by a sender of the email. The email body 202 can also identify the sender and the receiver and a time and a date the email was sent. As shown the email body 202 also includes a paperclip or similar icon 208B indicating there is at least one file attached the displayed email 200. As shown, multiple files are actually attached to the displayed email 200.

Below the email body 202 displayed email 200 is a thumbnail area 206 showing small iconic representations, often referred to as thumbnails, of the files attached to the displayed email 200. Between the thumbnail area 206 and the email body 202 is an area 212 including multiple functional buttons relating to the attached files. In this instance there are buttons for “View All” to view all of the attached files, and “Download All” to download all of the attached files. Also provided is a list that specifies there are 8 different attached files.

One of the attached files is “Environment.zip” 228 having a thumbnail that resembles a clamp compressing multiple sheets of paper to indicate Environment.zip is a compressed file including multiple individual files. It should be understood that there are many different iconic representations of a compressed file and this is merely one example of a compressed file attachment.

The compressed file attachment Environment.zip is selected and a file structure 204 of Environment.zip is shown to the right of the email body 202. The .zip suffix indicates the Environment.zip file is a compressed file including one or more individual files and can also include a file structure organizing the individual files. It should be understood that “.zip” type files are one example of a compressed file but there are many different types of compressed files and the processes described herein are applicable to each different types of compressed files. As displayed the Environment.zip file includes a file structure 204 of three individual files 230, 232 and 234 in a top-level folder and two subfolders: Insurance 236 and Last weekend 238. Each of the two subfolders Insurance 236 and Last weekend 238 can include multiple individual files that are not shown in this preview of the file structure 204.

The user can utilize the user interface 122 to navigate to and select one of the individual files such as DSC1100.jpg 230. FIGS. 3-5 are screen captures of the displayed email 200 after having selected the individual file DSC1100.jpg 230, in accordance with embodiments of the present disclosure. Selecting DSC1100.jpg 230 causes the selected file to be displayed to the right of the email body 202 as shown in FIG. 3. The file structure 204 can also be seen. In this instance DSC1100.jpg is a drawing that was presented during the meetup that is the subject of the displayed email 200.

In FIG. 4, the file structure 204 is hidden and the individual file DSC1100.jpg 230 is shown more clearly. In FIG. 5, the file structure 204 is again shown and the user is shown navigating the file structure to select the feedbackform.pdf 234. The file structure can be selected by selecting a corner of the DSC1100.jpg or by selecting another icon for displaying the file structure or by selecting the “Environment.zip” above the displayed DSC1100.jpg 230.

FIGS. 6 and 7 are screen captures of a displayed email 200 after having selected the individual file feedbackform.pdf 234, in accordance with embodiments of the present disclosure. Selecting feedbackform.pdf 234 causes a preview of the selected file to be displayed to the right of the email body 202. In FIG. 7, a subfolder file structure 238 is shown and the user has navigated the file structure to select another subfolder file structure entitled “Selected” 255. Selecting Selected 255 opens the subfolder entitled “Selected.” Within the Selected subfolder is a file entitled “selectedshot.jpg” 260.

FIG. 8A is a screen capture of a displayed email 200 after having selected the selectedshot.jpg 260, in accordance with embodiments of the present disclosure. Selecting selectedshot.jpg 260 causes the selectedshot.jpg to be displayed to the right of the email body 202. The directory structure 270 and access the selectedshot.jpg 260 is optionally shown directly above the selectedshot.jpg.

The selectedshot.jpg 260 can also be shown in full screen view. The selectedshot.jpg 260 can also be shown in full screen view. FIG. 8B is a screen capture of a displayed email 200 with a full screen view of the selectedshot.jpg 260, in accordance with embodiments of the present disclosure.

FIG. 9 is a processing flow diagram of the email server 110, in accordance with embodiments of the present disclosure. The email server 110 includes a front end 111, a middle tier 114, a storage tier 113, and a processing tier 115. The front end 111 receives the email and includes a user interface module for communicating with a user interface 122 on a client device. The middle tier 114 directs the email to the appropriate portion of the email server 110. The storage tier 113 provides the data storage for the email server 110. The storage tier 113 can also include or be coupled to the store facility 112 described above FIG. 1. The processing tier 115 provides the needed processing functionality of the email that is received or decompressed or sent or stored.

Returning to our example above with a compressed file attached to an email, an email is received by the front end 111, with a compressed file attached. The front-end directs the received email to the middle tier 114. The middle tier 114 stores the email by directing the email to the storage tier 113. The middle tier 114 can also detect the presence of the compressed file attachment in the email and forward the email to the processing tier 115 for further processing.

The processing tier 115 receives the email with the compressed file attachment and extracts the compressed file attachment from the email and directs the compressed file attachment to the storage tier 113 for storage. The processing tier 115 also analyzes the compressed file attachment to determine the type of compressed file and what is necessary to decompress the compressed file attachment. By way of example, there are multiple types of file compression formats that may be included in the compressed file attachment. Returning to our previous example of Environment.zip in which the “.zip” defines the type of compression format of the Environment.zip file.

Once the processing tier 115 determines what functionality is necessary to decompress the compressed file attachment, the processing tier can perform a decompression of the compressed file attachment.

The processing tier 115 directs the resulting decompressed file attachment including the multiple individual files and any file structure to the storage tier 113 for storage. The processing tier 115 also forwards a list of the individual files in the file structure to the middle tier 114.

When a user selects to preview the compressed file attachment a request for the preview of the compressed file attachment is received by the front end 111. The front end 111 forwards the preview request of the compressed file attachment to the middle tier 114.

The middle tier responds to the preview request of the compressed file attachment by forwarding the list of individual files and the file structure included in the compressed file attachment to the front end 111. The front end 111 forwards the list of individual files and the file structure included in the compressed file attachment to the user interface 122. The user interface 122 presents the list of individual files and the file structure 204 as shown in FIG. 2 above. It should be understood that in some instances a preview of the compressed file attachment can be generated and displayed automatically similar to the presentation of previews of any non-compressed file attachments, as shown in the preview area 206 in FIG. 2 above.

When the user selects a preview of one of the individual files and/or the file structure included in the compressed file attachment, a request for the preview of the individual files and/or the file structure is received by the front end 111. The front end 111 forwards the preview request of the individual files and/or the file structure to the middle tier 114.

The middle tier 114 forwards the preview request of the individual files and/or the file structure to the processing tier 115. The processing tier 115 downloads the selected file and generates a preview of the selected file. As noted above, one type of preview is a thumbnail or similar visually small and/or simplified version of the selected file to represent the selected file that is suitable for presentation in the user interface 122. In one example, the preview can be an HTML type document or similar suitable document.

The processing tier 115 directs the generated preview and/or the file structure to the storage tier 113 for storage. The processing tier 115 also directs the generated preview and/or file structure to the middle tier 114. The middle tier 114 forwards the generated preview and/or file structure to the front end 111. The front end 111 forwards the generated preview and/or file structure to the user interface 122. The file preview can be displayed in the file preview portion to the right of the email body 202 as shown in FIGS. 3-8B above.

With the above embodiments in mind, it should be understood that the invention may employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing.

The invention may be practiced with other computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The invention may also be practiced in distributing computing environments where tasks are performed by remote processing devices that are linked through a network.

Any of the operations described herein that form part of the invention are useful machine operations. The invention also relates to a device or an apparatus for performing these operations. The apparatus may be specially constructed for the required purpose, such as a special purpose computer. When defined as a special purpose computer, the computer can also perform other processing, program execution or routines that are not part of the special purpose, while still being capable of operating for the special purpose. Alternatively, the operations may be processed by a general purpose computer selectively activated or configured by one or more computer programs stored in the computer memory, cache, or obtained over a network. When data is obtained over a network the data maybe processed by other computers on the network, e.g., a cloud of computing resources.

The embodiments of the present invention can also be defined as a machine that transforms data from one state to another state. The transformed data can be saved to storage and then manipulated by a processor. The processor thus transforms the data from one thing to another. Still further, the methods can be processed by one or more machines or processors that can be connected over a network. Each machine can transform data from one state or thing to another, and can also process data, save data to storage, transmit data over a network, display the result, or communicate the result to another machine.

The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, DVDs, Flash, magnetic tapes, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims. 

What is claimed is:
 1. An email system comprising: an email server including: a front end for receiving an email from an email service coupled to the server by a network; a middle tier configured for detecting a compressed file attachment attached to a received email; a storage tier configured for storing a received email and the compressed file attachment; a processing tier including a decompressing process module configured for receiving the compressed file attachment, determining a type of compressed file attachment, determining a corresponding file decompression module from a plurality of file decompression modules, activating the corresponding file decompression module for decompressing the compressed file attachment to produce a decompressed file, storing the decompressed file in the storage tier and outputting the decompressed file to the middle tier; and a user interface module included in the front end tier and being configured for communicating with a user interface on a user client device to provide a user interface to the email server, the user interface configured for displaying a preview of the compressed file attachment and a preview of the decompressed file.
 2. The system of claim 1, wherein the front end includes
 3. The system of claim 1, wherein the middle tier includes
 4. The system of claim 1, wherein the processing tier includes
 5. The system of claim 1, wherein compressed file attachment includes a file structure for organizing at least one file included in the compressed file attachment.
 6. The system of claim 5, wherein processing tier is configured for detecting the file structure in the compressed file structure and storing the file structure and outputting a preview of the file structure.
 7. The system of claim 6, wherein the front end is configured for outputting the preview of the file structure to the user interface for display by the user interface.
 8. The system of claim 5, wherein the processing tier is configured for outputting the file structure and the front end is configured for outputting the file structure to the user interface for the user interface to display and provide a navigation of the file structure.
 9. The system of claim 1, wherein the processing tier produces the preview of the compressed file attachment when a compressed file preview request is received in the front end.
 10. The system of claim 1, wherein the processing tier produces the preview of the decompressed file when a file preview request is received in the front end.
 11. A method of generating a preview of a file attachment comprising: receiving an file attachment in an email server; determining if the file attachment is a previewable file type; and generating a preview of the file attachment including: identifying the file attachment; parsing the file attachment to identify content of the file attachment, wherein the identified content includes a pagination of the file attachment; creating a file structure for each page of the file attachment; and saving the file structure for each page of the file attachment to an attachment store in the email server.
 12. The method of claim 11, wherein identifying the file attachment includes generating a unique file identifier for the file attachment.
 13. The method of claim 11, wherein creating the file structure for each page of the file attachment includes defining a parent frame and a set of HTML data to create a preview for each page of the file attachment.
 14. The method of claim 11, wherein receiving the file attachment in the email server includes receiving a file to be attached to an email that is being composed on the email server.
 15. The method of claim 11, wherein receiving the file attachment in the email server includes receiving an email in the email server and detecting the file attachment attached to the received email.
 16. The method of claim 15, further comprising, at a time subsequent to the file attachment being received in the email server, email server receiving a request for a preview of a selected page of the file attachment and the email server serving the preview of the selected page of the file attachment to the requester.
 17. The method of claim 11, determining if the file attachment is a previewable file type includes: determining if the file attachment is a compressed file type; and decompressing the file attachment when the file attachment is a compressed file type including extracting one or more individual files from the file attachment.
 18. The method of claim 17, wherein generating the preview of the file attachment includes generating a preview of each one of the extracted one or more individual files from the file attachment.
 19. An email system comprising: an email server including: a front end for receiving a file attachment; a middle tier configured for detecting the file attachment; a storage tier including a file attachment store and being configured for storing the file attachment; and a processing tier including a file access module configured for accessing the file attachment, determining a file type of file attachment, identifying the file attachment, parsing the file attachment to identify a content of the file attachment including a pagination of the file attachment and generating a preview of each page of the file attachment and storing the preview of each page of the file attachment in the storage tier; and a user interface module configured to communicate with a user interface on a user client device. 